I may be reading too much into this but, Does this mean that at the end of a session you have the choice to commit the current ram overlay onto the CF, that it will become the new boot state?
No, not yet anyway.
When I want to update/write something permanently, I just type
rw first, and then perform whatever commands I want from within that shell -- the results are committed directly to the CF/disk from there. Or just copy stuff to anywhwere I like under the
/.rw/ tree.
But there are surprisingly few things in that category -- email is all on remote servers, and nothing from the web needs saving usually.
But I am also thinking now about a script to
commit (or "snapshot") the current RAM state to disk, permanently. It just means that a script is needed to loop over the
.tmpfs filesystem and copy/move stuff from there back to the permanent
/.rw/ CF/disk filesystem
(and handle deleted stuff as well). On command.
Cheers
Previous Topic
Index
